home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Network Support Library
/
RoseWare - Network Support Library.iso
/
email
/
widene.v2
< prev
next >
Wrap
Text File
|
1993-10-09
|
8KB
|
142 lines
REF: WIDENET2 2 Apr 1993
Using Notework over Wide-Area Networks (WANs)
The Wide Nets feature will appeal to you if you wish to prevent NWXBIND from
attaching to certain servers. Essentially, surrogate Notework directories
are created on a "local" server. Batch files are then used to gather, create,
and distribute the global Address Book to each of the "remote" servers. There
are three batch files used in the process, GETWIDE.BAT, PUTWIDE.BAT, and
WIDENET.BAT. The only file to which you will be making any changes is
WIDENET.BAT. WIDENET.BAT is the main batch file used in the Wide Nets feature;
it calls GETWIDE and PUTWIDE once for each remote server in your
configuration.
There are 3 possible configurations which you may encounter when setting up
Notework that call for a Wide Nets installation. Read the 3 possible
scenarios and decide which one is applicable to your site (if any). In all
cases, there are two servers (A and B) that are connected over a LAN, and a
third server (C) that is linked or bridged by a much slower line.
Scenario 1:
Servers A, B, and C are all new Notework installations. Running NWXBIND could
take a long time to complete and substantially slow down the link.
Scenario 2:
A cross-server installation has been up and running, but when running an
NWXBIND, server C takes a very long time to update and during the update, it
may cause communication over the slow line to come to a halt.
Scenario 3:
File servers A and B have been in a cross-server installation; file
server C is a brand new Notework installation and would like to be included
in cross-server mail. File server C has a slow or unreliable bridge to
servers A and B. NWXBIND may fail when the bridge is down and could cause
unwanted traffic across the bridge when running.
===== Scenario 1 Setup Instructions =====
1. Install Notework on servers A, B, and C.
2. On server A, create a subdirectory under \PUBLIC\NOTEWORK called XSERVE.
If there is more than one server connected to servers A and B via
a slow link, then create multiple directories under \PUBLIC\NOTEWORK and
name them XSERVE1, XSERVE2...... , with an XSERVE<x> directory for each
slow-linked server. The XSERVE<x> directories will act as surrogate Notework
directories.
3. On server A, create an ASCII file called XSERVERS.TXT. This file contains
the paths to all of the Notework system directories (for each server on
the LAN) plus the surrogate Notework directories (for each server that is
connected via a slow link). This file is like the "normal" XSERVERS.TXT
described under the topic "Installing on Multiple Servers", except that
for each slow-linked server, you create a line in XSERVERS.TXT which
looks like this:
"FILE_SERVER_C=FILE_SERVER_A/SYS:\PUBLIC\NOTEWORK\XSERVE". Do not include
the *true* path for each of the slow-linked servers in XSERVERS.TXT,
only include the surrogate
"<servername>=FILE_SERVER_A/SYS:\PUBLIC\NOTEWORK\XSERVE<x>" path.
Example:
FILE_SERVER_A/SYS:\PUBLIC\NOTEWORK
FILE_SERVER_B/SYS:\PUBLIC\NOTEWORK
FILE_SERVER_C=FILE_SERVER_A/SYS:\PUBLIC\NOTEWORK\XSERVE
4. Edit the WIDENET.BAT file on server A. For each slow-linked server,
WIDENET.BAT must call GETWIDE and PUTWIDE. The line which calls GETWIDE
or PUTWIDE must also contain the full path to the remote Notework
system directory followed by a space and the the path to its surrogate
directory.
5. Attach to all of the remote servers as Supervisor.
6. Run WIDENET.BAT from server A.
===== Scenario 2 Setup Instructions =====
1. On server A, create a subdirectory under \PUBLIC\NOTEWORK called XSERVE.
If there is more than one server connected to servers A and B via
slow links, then create multiple directories under \PUBLIC\NOTEWORK and
name them XSERVE1, XSERVE2...... , with an XSERVE<x> directory for each
slow-linked server. The XSERVE<x> directories will act as surrogate
Notework directories.
2. On all servers except A, delete the file XSERVERS.TXT in the Notework
system directory.
3. On server A, edit the ASCII file called XSERVERS.TXT. This file contains
the paths to all of the Notework system directories (for each server on
the LAN) plus the surrogate Notework directories (for each server that is
connected via a slow link). For each slow-linked server, change the line
in XSERVERS.TXT so that it looks like this:
"FILE_SERVER_C=FILE_SERVER_A/SYS:\PUBLIC\NOTEWORK\XSERVE". Do not put
the *true* path for each of the slow-linked servers in XSERVERS.TXT,
only include the surrogate
"<servername>=FILE_SERVER_A/SYS:\PUBLIC\NOTEWORK\XSERVE<x>" path.
Example:
FILE_SERVER_A/SYS:\PUBLIC\NOTEWORK
FILE_SERVER_B/SYS:\PUBLIC\NOTEWORK
FILE_SERVER_C=FILE_SERVER_A/SYS:\PUBLIC\NOTEWORK\XSERVE
4. Edit the WIDENET.BAT file on server A. For each slow-linked server,
WIDENET.BAT must call GETWIDE and PUTWIDE. The line which calls GETWIDE
or PUTWIDE must also contain the full path to the remote Notework system
directory followed by a space and the the path to its surrogate directory.
5. Attach to all of the remote servers as Supervisor.
6. Run WIDENET.BAT from server A.
===== Scenario 3 Setup Instructions =====
1. Install Notework on server C.
2. On server A, create a subdirectory under \PUBLIC\NOTEWORK called XSERVE.
If there is more than one server connected to servers A and B via
a slow link, then create multiple directories under \PUBLIC\NOTEWORK and
name them XSERVE1, XSERVE2...... , with an XSERVE<x> directory for each
slow-linked server. The XSERVE<x> directories will act as surrogate
Notework directories.
3. Delete XSERVERS.TXT from the Notework system directory on server B.
4. On server A edit the ASCII file called XSERVERS.TXT. This file contains
the paths to all of the Notework system directories (for each server on
the LAN) plus the surrogate Notework directories (for each server that is
connected via a slow link). For each slow-linked server, change the line
in XSERVERS.TXT so that it looks like this:
"FILE_SERVER_C=FILE_SERVER_A/SYS:\PUBLIC\NOTEWORK\XSERVE". Do not put
the *true* path for each of the slow-linked servers in XSERVERS.TXT,
only include the surrogate
"<servername>=FILE_SERVER_A/SYS:\PUBLIC\NOTEWORK\XSERVE<x>" path.
Example:
FILE_SERVER_A/SYS:\PUBLIC\NOTEWORK
FILE_SERVER_B/SYS:\PUBLIC\NOTEWORK
FILE_SERVER_C=FILE_SERVER_A/SYS:\PUBLIC\NOTEWORK\XSERVE
5. Edit the WIDENET.BAT file on server A. For each slow-linked server,
WIDENET.BAT must call GETWIDE and PUTWIDE. The line which calls GETWIDE
or PUTWIDE must also contain the full path to the remote Notework
system directory followed by a space and the the path to its surrogate
directory.
6 Attach to all of the remote servers as Supervisor.
7. Run WIDENET.BAT from server A.
===== Batch File Descriptions =====
WIDENET.BAT - This is the control file for the Wide Nets feature. It must
be customized by the network Supervisor for each installation. The
Supervisor specifies the number of times WIDENET.BAT runs GETWIDE and
PUTWIDE (one GETWIDE and PUTWIDE cycle is required for each remote server).
After all of the GETWIDE cycles have run, WIDENET.BAT runs the NWXBIND
utility to create the global Address Book, and PUTWIDE is then run to
distribute the Address Book files back to the remote directories.
GETWIDE.BAT - Collects files from the remote servers and copies them to the
local surrogate Notework directories. (No modification of this file is
necessary.)
PUTWIDE.BAT - Distributes global Address Book to the remote servers, and
runs NEWAP.EXE on each of the remote servers to create a new book directory
and update SYS.NWC. (No modification of this file is necessary.)